<!DOCTYPE html>
<html lang="en-us">
  <head>

    <meta http-equiv="content-type" content="text/html; charset=utf-8">
    
<meta charset="UTF-8">
<title>Hunspell Stemmer | Elasticsearch: The Definitive Guide [2.x] | Elastic</title>
<link rel="home" href="index.html" title="Elasticsearch: The Definitive Guide [2.x]">
<link rel="up" href="stemming.html" title="Reducing Words to Their Root Form">
<link rel="prev" href="dictionary-stemmers.html" title="Dictionary Stemmers">
<link rel="next" href="choosing-a-stemmer.html" title="Choosing a Stemmer">
<meta name="DC.type" content="Learn/Docs/Legacy/Elasticsearch/Definitive Guide/2.x">
<meta name="DC.subject" content="Elasticsearch">
<meta name="DC.identifier" content="2.x">
<meta name="robots" content="noindex,nofollow">
    <meta http-equiv="X-UA-Compatible" content="IE=edge">
    <meta name="viewport" content="width=device-width, initial-scale=1">
    <script src="https://cdn.optimizely.com/js/18132920325.js"></script>
    <link rel="apple-touch-icon" sizes="57x57" href="/apple-icon-57x57.png">
    <link rel="apple-touch-icon" sizes="60x60" href="/apple-icon-60x60.png">
    <link rel="apple-touch-icon" sizes="72x72" href="/apple-icon-72x72.png">
    <link rel="apple-touch-icon" sizes="76x76" href="/apple-icon-76x76.png">
    <link rel="apple-touch-icon" sizes="114x114" href="/apple-icon-114x114.png">
    <link rel="apple-touch-icon" sizes="120x120" href="/apple-icon-120x120.png">
    <link rel="apple-touch-icon" sizes="144x144" href="/apple-icon-144x144.png">
    <link rel="apple-touch-icon" sizes="152x152" href="/apple-icon-152x152.png">
    <link rel="apple-touch-icon" sizes="180x180" href="/apple-icon-180x180.png">
    <link rel="icon" type="image/png" href="/favicon-32x32.png" sizes="32x32">
    <link rel="icon" type="image/png" href="/android-chrome-192x192.png" sizes="192x192">
    <link rel="icon" type="image/png" href="/favicon-96x96.png" sizes="96x96">
    <link rel="icon" type="image/png" href="/favicon-16x16.png" sizes="16x16">
    <link rel="manifest" href="/manifest.json">
    <meta name="apple-mobile-web-app-title" content="Elastic">
    <meta name="application-name" content="Elastic">
    <meta name="msapplication-TileColor" content="#ffffff">
    <meta name="msapplication-TileImage" content="/mstile-144x144.png">
    <meta name="theme-color" content="#ffffff">
    <meta name="naver-site-verification" content="936882c1853b701b3cef3721758d80535413dbfd">
    <meta name="yandex-verification" content="d8a47e95d0972434">
    <meta name="localized" content="true">
    <meta name="st:robots" content="follow,index">
    <meta property="og:image" content="https://www.elastic.co/static/images/elastic-logo-200.png">
    <link rel="shortcut icon" href="/favicon.ico" type="image/x-icon">
    <link rel="icon" href="/favicon.ico" type="image/x-icon">
    <link rel="apple-touch-icon-precomposed" sizes="64x64" href="/favicon_64x64_16bit.png">
    <link rel="apple-touch-icon-precomposed" sizes="32x32" href="/favicon_32x32.png">
    <link rel="apple-touch-icon-precomposed" sizes="16x16" href="/favicon_16x16.png">
    <!-- Give IE8 a fighting chance -->
    <!--[if lt IE 9]>
    <script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js"></script>
    <script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script>
    <![endif]-->
    <link rel="stylesheet" type="text/css" href="/guide/static/styles.css">
  </head>

  <!--© 2015-2021 Elasticsearch B.V. Copying, publishing and/or distributing without written permission is strictly prohibited.-->

  <body>
    <!-- Google Tag Manager -->
    <script>dataLayer = [];</script><noscript><iframe src="//www.googletagmanager.com/ns.html?id=GTM-58RLH5" height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>
    <script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start': new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0], j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src= '//www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f); })(window,document,'script','dataLayer','GTM-58RLH5');</script>
    <!-- End Google Tag Manager -->

    <!-- Global site tag (gtag.js) - Google Analytics -->
    <script async src="https://www.googletagmanager.com/gtag/js?id=UA-12395217-16"></script>
    <script>
      window.dataLayer = window.dataLayer || [];
      function gtag(){dataLayer.push(arguments);}
      gtag('js', new Date());
      gtag('config', 'UA-12395217-16');
    </script>

    <!--BEGIN QUALTRICS WEBSITE FEEDBACK SNIPPET-->
    <script type="text/javascript">
      (function(){var g=function(e,h,f,g){
      this.get=function(a){for(var a=a+"=",c=document.cookie.split(";"),b=0,e=c.length;b<e;b++){for(var d=c[b];" "==d.charAt(0);)d=d.substring(1,d.length);if(0==d.indexOf(a))return d.substring(a.length,d.length)}return null};
      this.set=function(a,c){var b="",b=new Date;b.setTime(b.getTime()+6048E5);b="; expires="+b.toGMTString();document.cookie=a+"="+c+b+"; path=/; "};
      this.check=function(){var a=this.get(f);if(a)a=a.split(":");else if(100!=e)"v"==h&&(e=Math.random()>=e/100?0:100),a=[h,e,0],this.set(f,a.join(":"));else return!0;var c=a[1];if(100==c)return!0;switch(a[0]){case "v":return!1;case "r":return c=a[2]%Math.floor(100/c),a[2]++,this.set(f,a.join(":")),!c}return!0};
      this.go=function(){if(this.check()){var a=document.createElement("script");a.type="text/javascript";a.src=g;document.body&&document.body.appendChild(a)}};
      this.start=function(){var a=this;window.addEventListener?window.addEventListener("load",function(){a.go()},!1):window.attachEvent&&window.attachEvent("onload",function(){a.go()})}};
      try{(new g(100,"r","QSI_S_ZN_emkP0oSe9Qrn7kF","https://znemkp0ose9qrn7kf-elastic.siteintercept.qualtrics.com/WRSiteInterceptEngine/?Q_ZID=ZN_emkP0oSe9Qrn7kF")).start()}catch(i){}})();
    </script><div id="ZN_emkP0oSe9Qrn7kF"><!--DO NOT REMOVE-CONTENTS PLACED HERE--></div>
    <!--END WEBSITE FEEDBACK SNIPPET-->

    <div id="elastic-nav" style="display:none;"></div>
    <script src="https://www.elastic.co/elastic-nav.js"></script>

    <!-- Subnav -->
    <div>
      <div>
        <div class="tertiary-nav d-none d-md-block">
          <div class="container">
            <div class="p-t-b-15 d-flex justify-content-between nav-container">
              <div class="breadcrum-wrapper"><span><a href="/guide/" style="font-size: 14px; font-weight: 600; color: #000;">Docs</a></span></div>
            </div>
          </div>
        </div>
      </div>
    </div>

    <div class="main-container">
      <section id="content">
        <div class="content-wrapper">

          <section id="guide" lang="en">
            <div class="container">
              <div class="row">
                <div class="col-xs-12 col-sm-8 col-md-8 guide-section">
                  <!-- start body -->
                  <div class="page_header">
<p>
  <strong>WARNING</strong>: The 2.x versions of Elasticsearch have passed their
  <a href="https://www.elastic.co/support/eol">EOL dates</a>. If you are running
  a 2.x version, we strongly advise you to upgrade.
</p>
<p>
  This documentation is no longer maintained and may be removed. For the latest
  information, see the <a href="https://www.elastic.co/guide/en/elasticsearch/reference/current/index.html">current
  Elasticsearch documentation</a>.
</p>
</div>
<div id="content">
<div class="breadcrumbs">
<span class="breadcrumb-link"><a href="index.html">Elasticsearch: The Definitive Guide [2.x]</a></span>
»
<span class="breadcrumb-link"><a href="languages.html">Dealing with Human Language</a></span>
»
<span class="breadcrumb-link"><a href="stemming.html">Reducing Words to Their Root Form</a></span>
»
<span class="breadcrumb-node">Hunspell Stemmer</span>
</div>
<div class="navheader">
<span class="prev">
<a href="dictionary-stemmers.html">« Dictionary Stemmers</a>
</span>
<span class="next">
<a href="choosing-a-stemmer.html">Choosing a Stemmer »</a>
</span>
</div>
<div class="section">
<div class="titlepage"><div><div>
<h2 class="title">
<a id="hunspell"></a>Hunspell Stemmer<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/elasticsearch-definitive-guide/edit/2.x/230_Stemming/30_Hunspell_stemmer.asciidoc">edit</a>
</h2>
</div></div></div>
<p>Elasticsearch provides dictionary-based stemming via the
<a href="/guide/en/elasticsearch/reference/2.4/analysis-hunspell-tokenfilter.html" class="ulink" target="_top"><code class="literal">hunspell</code> token filter</a>.
Hunspell <a href="http://hunspell.github.io/" class="ulink" target="_top"><em>hunspell.github.io</em></a> is the
spell checker used by Open Office, LibreOffice, Chrome, Firefox, Thunderbird, and many
other open and closed source projects.</p>
<p>Hunspell dictionaries can be obtained from the following:</p>
<div class="ulist itemizedlist">
<ul class="itemizedlist">
<li class="listitem">
<a href="http://extensions.openoffice.org/" class="ulink" target="_top"><em>extensions.openoffice.org</em></a>: Download and
unzip the <code class="literal">.oxt</code> extension file.
</li>
<li class="listitem">
<a href="http://mzl.la/157UORf" class="ulink" target="_top"><em>addons.mozilla.org</em></a>:
Download and unzip the <code class="literal">.xpi</code> addon file.
</li>
<li class="listitem">
<a href="http://download.services.openoffice.org/contrib/dictionaries/" class="ulink" target="_top">OpenOffice archive</a>: Download and unzip the <code class="literal">.zip</code> file.
</li>
</ul>
</div>
<p>A Hunspell dictionary consists of two files with the same base name—​such as
<code class="literal">en_US</code>—but with one of two extensions:</p>
<div class="variablelist">
<dl class="variablelist">
<dt>
<span class="term">
<code class="literal">.dic</code>
</span>
</dt>
<dd>
Contains all the root words, in alphabetical order, plus a code representing
all possible suffixes and prefixes (which collectively are known as <em>affixes</em>)
</dd>
<dt>
<span class="term">
<code class="literal">.aff</code>
</span>
</dt>
<dd>
Contains the actual prefix or suffix transformation for each code listed
in the <code class="literal">.dic</code> file
</dd>
</dl>
</div>
<div class="section">
<div class="titlepage"><div><div>
<h3 class="title">
<a id="_installing_a_dictionary"></a>Installing a Dictionary<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/elasticsearch-definitive-guide/edit/2.x/230_Stemming/30_Hunspell_stemmer.asciidoc">edit</a>
</h3>
</div></div></div>
<p>The Hunspell token filter looks for dictionaries within a dedicated Hunspell
directory, which defaults to  <code class="literal">./config/hunspell/</code>. The <code class="literal">.dic</code> and <code class="literal">.aff</code>
files should be placed in a subdirectory whose name represents the language
or locale of the dictionaries.  For instance, we could create a Hunspell
stemmer for American English with the following layout:</p>
<div class="pre_wrapper lang-text">
<pre class="programlisting prettyprint lang-text">config/
  └ hunspell/ <a id="CO156-1"></a><i class="conum" data-value="1"></i>
      └ en_US/ <a id="CO156-2"></a><i class="conum" data-value="2"></i>
          ├ en_US.dic
          ├ en_US.aff
          └ settings.yml <a id="CO156-3"></a><i class="conum" data-value="3"></i></pre>
</div>
<div class="calloutlist">
<table border="0" summary="Callout list">
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO156-1"><i class="conum" data-value="1"></i></a></p>
</td>
<td align="left" valign="top">
<p>The location of the Hunspell directory can be changed by setting
<code class="literal">indices.analysis.hunspell.dictionary.location</code> in the
<code class="literal">config/elasticsearch.yml</code> file.</p>
</td>
</tr>
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO156-2"><i class="conum" data-value="2"></i></a></p>
</td>
<td align="left" valign="top">
<p><code class="literal">en_US</code> will be the name of the locale or <code class="literal">language</code> that we pass to the
<code class="literal">hunspell</code> token filter.</p>
</td>
</tr>
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO156-3"><i class="conum" data-value="3"></i></a></p>
</td>
<td align="left" valign="top">
<p>Per-language settings file, described in the following section.</p>
</td>
</tr>
</table>
</div>
</div>

<div class="section">
<div class="titlepage"><div><div>
<h3 class="title">
<a id="_per_language_settings"></a>Per-Language Settings<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/elasticsearch-definitive-guide/edit/2.x/230_Stemming/30_Hunspell_stemmer.asciidoc">edit</a>
</h3>
</div></div></div>
<p>The <code class="literal">settings.yml</code> file contains settings that apply to all of the
dictionaries within the language directory, such as these:</p>
<div class="pre_wrapper lang-yaml">
<pre class="programlisting prettyprint lang-yaml">---
ignore_case:          true
strict_affix_parsing: true</pre>
</div>
<p>The meaning of these settings is as follows:</p>
<div class="variablelist">
<dl class="variablelist">
<dt>
<span class="term">
<code class="literal">ignore_case</code>
</span>
</dt>
<dd>
<p>Hunspell dictionaries are case sensitive by default: the surname <code class="literal">Booker</code> is a
different word from the noun <code class="literal">booker</code>, and so should be stemmed differently.  It
may seem like a good idea to use the <code class="literal">hunspell</code> stemmer in case-sensitive
mode, but that can complicate things:</p>
<div class="ulist itemizedlist">
<ul class="itemizedlist">
<li class="listitem">
A word at the beginning of a sentence will be capitalized, and thus appear
to be a proper noun.
</li>
<li class="listitem">
The input text may be all uppercase, in which case almost no words will be
found.
</li>
<li class="listitem">
The user may search for names in all lowercase, in which case no capitalized
words will be found.
</li>
</ul>
</div>
<p>As a general rule, it is a good idea to set <code class="literal">ignore_case</code> to <code class="literal">true</code>.</p>
</dd>
<dt>
<span class="term">
<code class="literal">strict_affix_parsing</code>
</span>
</dt>
<dd>
The quality of dictionaries varies greatly. Some dictionaries that are
available online have malformed rules in the <code class="literal">.aff</code> file.  By default, Lucene
will throw an exception if it can’t parse an affix rule. If you need to deal
with a broken affix file, you can set <code class="literal">strict_affix_parsing</code> to <code class="literal">false</code> to tell
Lucene to ignore the broken rules.
</dd>
</dl>
</div>
<div class="sidebar">
<div class="titlepage"><div><div>
<p class="title"><strong>Custom Dictionaries</strong></p>
</div></div></div>
<p>If multiple dictionaries (<code class="literal">.dic</code> files) are placed in the same
directory, they will be merged together at load time. This allows you to
tailor the downloaded dictionaries with your own custom word lists:</p>
<div class="pre_wrapper lang-text">
<pre class="programlisting prettyprint lang-text">config/
  └ hunspell/
      └ en_US/  <a id="CO157-1"></a><i class="conum" data-value="1"></i>
          ├ en_US.dic
          ├ en_US.aff <a id="CO157-2"></a><i class="conum" data-value="2"></i>
          ├ custom.dic
          └ settings.yml</pre>
</div>
<div class="calloutlist">
<table border="0" summary="Callout list">
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO157-1"><i class="conum" data-value="1"></i></a></p>
</td>
<td align="left" valign="top">
<p>The <code class="literal">custom</code> and <code class="literal">en_US</code> dictionaries will be merged.</p>
</td>
</tr>
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO157-2"><i class="conum" data-value="2"></i></a></p>
</td>
<td align="left" valign="top">
<p>Multiple <code class="literal">.aff</code> files are not allowed, as they could use
conflicting rules.</p>
</td>
</tr>
</table>
</div>
<p>The format of the <code class="literal">.dic</code> and <code class="literal">.aff</code> files is discussed in
<a class="xref" href="hunspell.html#hunspell-dictionary-format" title="Hunspell Dictionary Format">Hunspell Dictionary Format</a>.</p>
</div>
</div>

<div class="section">
<div class="titlepage"><div><div>
<h3 class="title">
<a id="_creating_a_hunspell_token_filter"></a>Creating a Hunspell Token Filter<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/elasticsearch-definitive-guide/edit/2.x/230_Stemming/30_Hunspell_stemmer.asciidoc">edit</a>
</h3>
</div></div></div>
<p>Once your dictionaries are installed on all nodes, you can define a <code class="literal">hunspell</code>
token filter that uses them:</p>
<div class="pre_wrapper lang-json">
<pre class="programlisting prettyprint lang-json">PUT /my_index
{
  "settings": {
    "analysis": {
      "filter": {
        "en_US": {
          "type":     "hunspell",
          "language": "en_US" <a id="CO158-1"></a><i class="conum" data-value="1"></i>
        }
      },
      "analyzer": {
        "en_US": {
          "tokenizer":  "standard",
          "filter":   [ "lowercase", "en_US" ]
        }
      }
    }
  }
}</pre>
</div>
<div class="calloutlist">
<table border="0" summary="Callout list">
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO158-1"><i class="conum" data-value="1"></i></a></p>
</td>
<td align="left" valign="top">
<p>The <code class="literal">language</code> has the same name as the directory where
the dictionary lives.</p>
</td>
</tr>
</table>
</div>
<p>You can test the new analyzer with the <code class="literal">analyze</code> API,
and compare its output to that of the <code class="literal">english</code> analyzer:</p>
<div class="pre_wrapper lang-json">
<pre class="programlisting prettyprint lang-json">GET /my_index/_analyze?analyzer=en_US <a id="CO159-1"></a><i class="conum" data-value="1"></i>
reorganizes

GET /_analyze?analyzer=english <a id="CO159-2"></a><i class="conum" data-value="2"></i>
reorganizes</pre>
</div>
<div class="calloutlist">
<table border="0" summary="Callout list">
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO159-1"><i class="conum" data-value="1"></i></a></p>
</td>
<td align="left" valign="top">
<p>Returns <code class="literal">organize</code></p>
</td>
</tr>
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO159-2"><i class="conum" data-value="2"></i></a></p>
</td>
<td align="left" valign="top">
<p>Returns <code class="literal">reorgan</code></p>
</td>
</tr>
</table>
</div>
<p>An interesting property of the <code class="literal">hunspell</code> stemmer, as can be seen in the
preceding example, is that it can remove prefixes as well as as suffixes. Most
algorithmic stemmers remove suffixes only.</p>
<div class="tip admon">
<div class="icon"></div>
<div class="admon_content">
<p>Hunspell dictionaries can consume a few megabytes of RAM.  Fortunately,
Elasticsearch creates only a single instance of a dictionary per node.  All
shards that use the same Hunspell analyzer share the same instance.</p>
</div>
</div>
</div>

<div class="section">
<div class="titlepage"><div><div>
<h3 class="title">
<a id="hunspell-dictionary-format"></a>Hunspell Dictionary Format<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/elasticsearch-definitive-guide/edit/2.x/230_Stemming/30_Hunspell_stemmer.asciidoc">edit</a>
</h3>
</div></div></div>
<p>While it is not necessary to understand the format of a Hunspell dictionary in
order to use the <code class="literal">hunspell</code> tokenizer, understanding the format will help you
write your own custom dictionaries.  It is quite simple.</p>
<p>For instance, in the US English dictionary, the <code class="literal">en_US.dic</code> file contains an entry for
the word <code class="literal">analyze</code>, which looks like this:</p>
<div class="pre_wrapper lang-text">
<pre class="programlisting prettyprint lang-text">analyze/ADSG</pre>
</div>
<p>The <code class="literal">en_US.aff</code> file contains the prefix or suffix rules for the <code class="literal">A</code>, <code class="literal">G</code>,
<code class="literal">D</code>, and <code class="literal">S</code> flags.  Each flag consists of a number of rules, only one of
which should match. Each rule has the following format:</p>
<div class="pre_wrapper lang-text">
<pre class="programlisting prettyprint lang-text">[type] [flag] [letters to remove] [letters to add] [condition]</pre>
</div>
<p>For instance, the following is suffix (<code class="literal">SFX</code>) rule <code class="literal">D</code>.  It says that,  when a
word ends in a consonant (anything but <code class="literal">a</code>, <code class="literal">e</code>, <code class="literal">i</code>, <code class="literal">o</code>, or <code class="literal">u</code>) followed by
a <code class="literal">y</code>, it can have the <code class="literal">y</code> removed and <code class="literal">ied</code> added (for example, <code class="literal">ready</code> →
<code class="literal">readied</code>).</p>
<div class="pre_wrapper lang-text">
<pre class="programlisting prettyprint lang-text">SFX    D      y   ied  [^aeiou]y</pre>
</div>
<p>The rules for the <code class="literal">A</code>, <code class="literal">G</code>, <code class="literal">D</code>, and <code class="literal">S</code> flags mentioned previously are as follows:</p>
<div class="pre_wrapper lang-text">
<pre class="programlisting prettyprint lang-text">SFX D Y 4
SFX D   0     d          e <a id="CO160-1"></a><i class="conum" data-value="1"></i>
SFX D   y     ied        [^aeiou]y
SFX D   0     ed         [^ey]
SFX D   0     ed         [aeiou]y

SFX S Y 4
SFX S   y     ies        [^aeiou]y
SFX S   0     s          [aeiou]y
SFX S   0     es         [sxzh]
SFX S   0     s          [^sxzhy] <a id="CO160-2"></a><i class="conum" data-value="2"></i>

SFX G Y 2
SFX G   e     ing        e <a id="CO160-3"></a><i class="conum" data-value="3"></i>
SFX G   0     ing        [^e]

PFX A Y 1
PFX A   0     re         . <a id="CO160-4"></a><i class="conum" data-value="4"></i></pre>
</div>
<div class="calloutlist">
<table border="0" summary="Callout list">
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO160-1"><i class="conum" data-value="1"></i></a></p>
</td>
<td align="left" valign="top">
<p><code class="literal">analyze</code> ends in an <code class="literal">e</code>, so it can become <code class="literal">analyzed</code> by adding a <code class="literal">d</code>.</p>
</td>
</tr>
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO160-2"><i class="conum" data-value="2"></i></a></p>
</td>
<td align="left" valign="top">
<p><code class="literal">analyze</code> does not end in <code class="literal">s</code>, <code class="literal">x</code>, <code class="literal">z</code>, <code class="literal">h</code>, or <code class="literal">y</code>, so it can become
<code class="literal">analyzes</code> by adding an <code class="literal">s</code>.</p>
</td>
</tr>
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO160-3"><i class="conum" data-value="3"></i></a></p>
</td>
<td align="left" valign="top">
<p><code class="literal">analyze</code> ends in an <code class="literal">e</code>, so it can become <code class="literal">analyzing</code> by removing the <code class="literal">e</code>
and adding <code class="literal">ing</code>.</p>
</td>
</tr>
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO160-4"><i class="conum" data-value="4"></i></a></p>
</td>
<td align="left" valign="top">
<p>The prefix <code class="literal">re</code> can be added to form <code class="literal">reanalyze</code>. This rule can be
combined with the suffix rules to form <code class="literal">reanalyzes</code>, <code class="literal">reanalyzed</code>,
<code class="literal">reanalyzing</code>.</p>
</td>
</tr>
</table>
</div>
<p>More information about the Hunspell syntax can be found on the <a href="http://sourceforge.net/projects/hunspell/files/Hunspell/Documentation/" class="ulink" target="_top">Hunspell documentation site</a>.</p>
</div>

</div>
<div class="navfooter">
<span class="prev">
<a href="dictionary-stemmers.html">« Dictionary Stemmers</a>
</span>
<span class="next">
<a href="choosing-a-stemmer.html">Choosing a Stemmer »</a>
</span>
</div>
</div>

                  <!-- end body -->
                </div>
                <div class="col-xs-12 col-sm-4 col-md-4" id="right_col">
                  <div id="rtpcontainer" style="display: block;">
                    <div class="mktg-promo">
                      <h3>Most Popular</h3>
                      <ul class="icons">
                        <li class="icon-elasticsearch-white"><a href="https://www.elastic.co/webinars/getting-started-elasticsearch?baymax=default&amp;elektra=docs&amp;storm=top-video">Get Started with Elasticsearch: Video</a></li>
                        <li class="icon-kibana-white"><a href="https://www.elastic.co/webinars/getting-started-kibana?baymax=default&amp;elektra=docs&amp;storm=top-video">Intro to Kibana: Video</a></li>
                        <li class="icon-logstash-white"><a href="https://www.elastic.co/webinars/introduction-elk-stack?baymax=default&amp;elektra=docs&amp;storm=top-video">ELK for Logs &amp; Metrics: Video</a></li>
                      </ul>
                    </div>
                  </div>
                </div>
              </div>
            </div>
          </section>

        </div>


<div id="elastic-footer"></div>
<script src="https://www.elastic.co/elastic-footer.js"></script>
<!-- Footer Section end-->

      </section>
    </div>

<script src="/guide/static/jquery.js"></script>
<script type="text/javascript" src="/guide/static/docs.js"></script>
<script type="text/javascript">
  window.initial_state = {}</script>
  </body>
</html>
